

				Windows easyAGENT v1.1 & v1.2
				-----------------------------
				      Amilcar Hernandez
					July 15, 2008


Installation Instructions:
--------------------------

To install the approprate version of the Windows easyAGENT, indentify which version of the .NET 
Framework is installed on the target server by doing the following:

Start -> Run -> C:\Windows\Microsoft.NET\Framework

If the sever has v1.1 or v2.0 of the .NET Framework installed and easyAGENT is currently running on 
the 
server, please refer to the dotNET v1.1 Binary folder where you will find instructions on how to 
replace the existing easyAGENT service with the new binary.

If the server has v1.1 of the .NET Framework ONLY and 
easyAGENT is NOT installed on the server, please 
refer to the dotNET v1.1 Installer folder where you will instructions on how to install easyAGENT.

If the server has v2.0 of the .NET Framework and easyAGENT is NOT installed on the server, please
refer to the dotNET v2.0 Installer folder where you will find instructions on how to install easyAGENT.


Prerequisites for easyAGENT's New HP Checks:
--------------------------------------------

In order to perform any easyAGENT HP Checks, the target server must have the HP Insight Management 
WBEM Providers for Windows Server 2003/2008.  The HP Insight Management WBEM Providers supply system 
management data through the Windows Management Instrumentation framework for ProLiant server platforms
and options. 

To download this component visit the following web-site:

- For x32 Bit:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=428936&swItem=MTX-7a41e219f422484382008abb3a&prodNameId=3288114&swEnvOID=1005&swLang=8&taskId=135&mode=3

- For x64 Bit
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-79afcbd879444894afc90b3a9d&prodTypeId=15351&prodSeriesId=428936

After downloading and installing this component on the target server, you may begin creating easyAGENT 
HP Checks in Observer for the system.



easyAGENT's New HP Checks:
--------------------------

1: HpSystemStatus - Checks the HealthState on the following HP hardware components:
	
	* PowerSupply
	* MemoryModule or Memory
	* Processor
	* Fan

   The default value for this check is All, but if you wish to check just one of these hardware 
   components, you may specify the component in the argument text-box.

	Here is the list of arguments for this check.
	
	component = [component] component to monitor

	Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   	Observer. 
	
	component=All			Here we want to check all components on the server.
	component=MemoryModule		Here we want to check just the MemoryModule on the server.

2: HpEthernetPortStatus - Checks the HealtState of the onboard ethernet ports and PCI Ethernet card on 
   the target server.  You can specify either the port number you want to check or leave the default 
   value All.  If you issue this check and specify All, and one of the ethernert ports does not have 
   link, a WARNING state will be returned specifying the Ethernet port that has the no-link status, 
   therefore you will have to issue this check by only targeting the ports that have link.

	Here is the list of arguments for this check.
	
	portNumber = [number] either All or a port number

	Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   	Observer. 

	1	Here we want to monitor port 1 on the server.
	All	Here wer want to monitor all ports including PCI nic cards on the server.

3: HpArraySystemStatus - Checks the Operational Status of the onboard array card.
   
   There are no arguments associated with this check

4: HpLogicalDriveStatus - Checks the status of the array logical drives on the target system.  You can 
   specify 'system' to check the logical drives on the target server or specify 'msa' if the server has 
   an MSA attached.  for the MSA option, you must make sure that the Hpacucli is installed on the target
   server.  If the Hpacucli is not located in "C:\Program Files\Compaq\Hpacucli\Bin\hpacucli.exe"  You
   must supply the correct path in the value property on the easyAGENT.exe.config file located on root of
   the easyAGENT.  If the target server is an Exchange server, you will have to add the user that has been created
   to run the easyAGENT service on the Administrators Group thru computer management in order to configure this check
   for an msa, if this is not the case disregard this additional step.
   

	Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
	Observer. 	


	system		- Checks to logical drives on the target server.
	msa		- Checks all the logical drives attach to the MSA
	


Prerequisites for easyAGENT's New Exchange Checks:
--------------------------------------------------

In order to perform Exchange checks, the easyAGENT service must be configured to run under a Domain User
account that has the "View-Only-Admin" rights assigned to it via Exchange.  This account must have priviledges
in the HPQ, CIMV2, and MicrosoftExchangeV2 namespaces via WMI to run the standard, HP, and Exchange checks.
To give this account the WMI priviledges, do the following:

Start - Run - wmimgmt.msc
Right-click the WMI Control(Local) option at the top left, click properties, then click on the Security Tab,
Expand the root folder, click on one of three data repositories mentioned above, then click Security, Add the user you created to 
the group of user names, give this user the following permissions:
1: Execute Methods
2: Provider Write
3: Enable Account

Repeat this for the remaining two.

Hit OK, OK then close the WMI Infastructure, and you are done.

You must also add this account to the Performance Log Users group under Active Directory
 located on the Builtin folder.
If the server is not a domain crotroller but part of a domain, you must add the monitoring account to the Performance Log Users grous
in the local machine as well. 


easyAGENT's New Exchange Checks:
--------------------------------
 
1: ExchangeMailboxState - Iterates thru all the exchange mailboxes, and checks either the size or the 
   number of items of each mailbox and returns a state based on the warning level and critical level 
   specified by the user.  This check ignores the SystemMailbox, SMTP, and System Attendant mailbox instances.
   Here is the list of arguments for this check.

	filterType = [type] filter type, either size or items
	warningLevel = [KB] warning level threshold
	criticalLevel =[KB] critical level threshold

   Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer. 
	
	filterType=size, warningLevel=400, criticalLevel=500    -  In this case we want to check which mailboxes are over 400 or 500 KB.
	filterType=items, warningLevel=50, criticalLevel=60     -  In this case we want to check which mailboxes are over 50 or 60 Items.

2: ExchangeSmtpQueueState - Iterates thru one or all the Exchange SMTP Queues, and checks the size or
   number of messages of each SMTP Queue and returns a state based on the warning level and critical level
   specified by the user.  Here is a list of all the Exchange SMTP Queues that can be monitored in this check.


	* All				-  Iterates thru all the Exchange SMTP Queues	
	* LocalAsyncQueue		-  Local delivery
	* PreSubmissionQueue		-  Messages pending submission
	* PreCatQueue			-  Messages awaiting directory lookup
	* PreRoutingQueue		-  Messages waiting to be routed
	* PostDSNGenerationQueue	-  DSN messages pending submission
	* DeferredDeliveryQueue		-  Messages queued for deferred delivery
	* FailedMessageQueue		-  Failed message retry queue

   Here is the list of arguments for this check:

	filterType = [type] filter type, either size or items
	queueName = [type] Name of SMTP Queue
	warningLevel = [KB] warning level threshold
	criticalLevel = [KB] critical level threshold

   Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer. 
	
	filterType=size, queueName=All, warningLevel=400, criticalLevel=500    

        In the above statement we want to check all Exchange SMTP queues that are over 400 or 500 KB.

	filterType=items, queueName=LocalAsyncQueue, warningLevel=35, criticalLevel=45    
	
	In the above statement we want to check if the Local delivery queue goes over 35 or 45 number of messages.
	
3: ExchangePublicFolderState - Iterates thru all the Exchange Pubic Folders, and checks either the size 
   or the number of items of each public folder and returns a state based on the warning level and 
   critical level specified by the user.  Here is the list of arguments for this check.

	
	filterType = [type] filter type, either size or items
	warningLevel = [KB] warning level threshold
	criticalLevel = [KB] critical level threshold

   Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer. 
	
	filterType=size, warningLevel=400, criticalLevel=500    -  In this case we want to check which public folders are over 400 or 500 KB.
	filterType=items, warningLevel=50, criticalLevel=60     -  In this case we want to check which public folders are over 50 or 60 Items.

4:  ExchangeMailboxAggregateSize - Iterates thru all the Exchange mailboxes obtaining the total aggregate size,
    returns a state based on the warning and critical levels specified by the user.  This check ignores the
    SystemMailbox, SMTP, and System Attendant mailbox instances.

	Here is the list of arguments for this check:

	warningLevel = [MB] warning level threshold
	criticalLevel =[MB] critical level threshold
	
   Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer. 

	warningLevel=300, criticalLevel=350
	
	In this case we want to check if the mailbox total aggregate size is over 300 or 350 MB.

5:  ExchangeMailboxCount - Iterates thru all the Exchange mailboxes and yields the the number of mailboxes
    found.  This check ignores the SystemMailbox, SMTP, and System Attendant mailbox instances.  This is check
    is only informational therefore it does not have any thresholds, the status is always going to be OK.

6:  ExchangeRpcClientReqeusts - Gets the number of RPC client requests made to the Exchange server and returns a state
    based on the warning and critical level specified by the user.


	Here is the list of arguments for this check:

	warningLevel = [count] warning level threshold
	criticalLevel =[count] critical level threshold
	
   Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer. 

	warningLevel=30, criticalLevel=35
	
	In this case we want to check if the number of RPC Request exceeds 30 or 35 client requests.

7:  ExchangeBackupStatus -  Iterates thur all the mail stores and public folder stores, and checks their time of last
    full and incremental backup, and returns a state based on the threshold specify by the user.  The logic implemented
    will fist check to see if a full backup ran within the IncrementalBackupThreshold hour specification, if it did then the store evaluated is fine, if not it
    will then check the last incremental backup and last full backup and compare them against the thresholds, if either one fails
    it would then generate an alert.  There are some cases where stores do not perform incremental backups, if this is the case, then
    the state of the check is determined by whether the full backup ran before the IncrementalBackupThreshold parameter.

	Here is the list of arguments for this check:

	fullBackupThreshold = [hours] full backup threshold
        incrementalBackupThreshold = [hours] incremental backup threshold

   Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer.			

	fullBackupThreshold=168, incrementalBackupTheshold=24

	In this case we want to check if the time of full backup exceeds 168 hours which is 7 days, and the time of incremental backup exceeds 24 hours.	

easyAGENT's New Standard Checks:
--------------------------------

1: SystemPerfCounterStatus - checks the current size or count of the following performance counters and
   returns a state based on the waning and critical level specified by the user.
  
   Here are the performance counters you can monitor.
	
	* PoolNonPagedBytes
	* FreeSystemPageTableEntries
	* ExchangeMemoryErrors			- Must have Exchange Server install
	* ExchangeMemoryHeapsWithErrors		- Must have Exchange Server install
	* ExchangeMemoryAdditionalHeaps		- Must have Exchange Server install


   Here is the list of arguments for this check.


	counterName =  [counter] Counter for monitoring
	warningLevel = [MB] warning level threshold
	criticalLevel =[MB] critical level threshold
  
  Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   Observer. 
	
	counterName=PoolNonPagedBytes, warningLevel=25, criticalLevel=30    
	
	In the above we want to check if the PoolNonPagedBytes counter has exceeded 25 or 30 MB.
	Note: warningLevel and criticalLevel are entered in MB only for the first two counters on the list.
	      The rest are entered as a numerical value ONLY.

	counterName=ExchangeMemoryErrors, warningLevel=5, criticalLevel=8
	
	In the above, we want to check if the number of ExchangeMemoryErrors has exceeded over 5 or 8
	
		
2: PingMonitor - issues a ping request to the target IP and returns a state based on the ping statistics
   and parametes specified by the user.  The following are the check's parameters:

	ip = [ip]The ip to ping.
	name = [displayName]The name to display in the check.
	crit_rtt = [ms]The critical threshold for round-trip time.
	crit_loss = [percent]The critical threshold for packet loss.
	warn_rtt = [ms]The warning threshold for round-trip time.
	warn_loss = [percent]The warning threshold for packet loss.
	packets = [count]The number of packets to send.

	Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   	Observer. 

	ip=63.131.140.4, name=dphostedexchange.com, crit_rtt=8, crit_loss=50, warn_rtt=5, warn_loss=30, packets=6

	Here we are pinging the specify ip with 6 packets, setting the critical rtt to 8ms and the warning to 5ms, as well
	as the critical percent of packet lost to 50 percent, and the warning to 30 percent.

3: ProcessMemoryUtilization - Iterates thru one or All running processes from all users, and checks memory consumption 
   returning a state based on the warning and critical levels specified by the user.  The check should 
   be entered in the following format:
	
   Here are the check's parameters:

	processName = [name] Process to monitor
	warningLevel = [KB] warning level threshold
	criticalLevel =[KB] critical level threshold

	Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   	Observer. 

	processName=All, warningLevel=300000, criticalLevel=400000

	In the above, we want to check all the processes that have exceeded 300,000 or 400,000 KB

	processName=sqlservr.exe, warningLevel=200000, criticalLevel=300000

	In the above, we want to check if the sqlservr.exe process has exceeded 200,000 or 300,000 KB

4: ApplicationPoolState - Returns the state of the specified application pool, anb based on the current state returns
   either an OK, WARNING, CRITICAL or UNKNOWN back to the user.

   Here are the check's parameters:

	ApplicationPoolName = [name] Name of the application pool to monitor

  In Observer, just specified the name of the application pool on the Application Pool Text Field, then hit Save.
  If the application pool you have specified does not exist, an UNKNOWN status will be retuned in Observer.

Note: If you are running easyAGENT in another user-context other than Local System, you will need to provide the account
      thats is running easyAGENT access to the W3SVC/AppPools via the IIS-Metabase by running the Metaacl.vbs script thats located in
      the easyAGENT Resources folder.

      To run this script, open the command line, locate the path in which the Metaacl script resides, and type the following command:
      cscript Metaacl.vbs
      type the following command to set the read rights:
      MetaACL "IIS://Localhost/W3SVC/AppPools" Domain\account R
      
      You will see a message that says that the rights have been added to the account, yo may now create the check, or if you
      have already created it the check, ODC it in Observer.  If after your ODC the check, it does not work, restart the easyAGENT service
      so that the metabase can get update it, then try to ODC the check once more.  If it does not work after this approach, please 
      contact me.

5.  EventLogEntryStatus - Alerts if an entry is written to the Event Viewer with a certain word on the source of the entry, and based on
    the entry type, the state of the check is determined.  In order to clear this check, you have to specify the minute-threshold parameter
    that will re-set the state of the check back to OK, therefore you must have a good idea of dealing with this particular entry so that
    you don't create a false-positive. 

    Here are the check's parameters:
	
	logName = [Name] Name of the log to monitor, either Application, Security or System.
        filter  = [Name] Word to look for in the source of the log entry.
        minuteThreshold [min] Minute threshold to clear the state of the check back to OK.

    Here is an example on how to configure the check in the Add Service Check window or in the Options tab in
   	Observer.

	logName=Application, filter=easyAGENT, 
minuteThreshold=60


	Here we will start monitoring the Application logs for any etries written with the word 'easyAGENT' on the source, and after
        an hour, the state of the check will be re-set to OK, clearing the check withing the hour, which has been specified by the user.
